diferencias en el campo: el texto de la página
[p]Here a To-Do list & suggestions for the h-node project development and alike:[/p]
[h2]h-node[/h2]
[list]
[*] [del]RSS feeds of the modifications[/del] (done!)[/*]
[p]Almost finished[/p]
[*] [b]mobile version of the website[/b][/*]
[p]Only for some pages, for example the home page, the hardware pages, the search page. This should be done by adding a parameter in the URL (perhaps at the end) and decide the CSS file that should be loaded (if no parameter is present than the website will be optimized for monitors)[/p]
[*] [b]continue internationalization[/b][/*]
[p]There are a lot of areas still in English[/p]
[*] [b]build a form to help the user to choose a device[/b][/*]
[p]Something better than the current cataloguing, cataloging, perhaps inside the home page. The form should also consider those devices that can be easily mixed up, for example the ones ith the same model name but different chipset, and alerting the user or not suggesting that hardware at all (for each device it should be possible to add such an alert by the users or by the administrators)[/p]
[*] [b]add the possibility to download a pdf file[/b][/*]
[p]Built on the fly for example with fpdf) of each device page and in case of the whole database (Luis Alberto is working on this :)[/p]
[*] [b]add new categories of hardware[/b][/*]
[p]What should be the next category?[/p]
[/list]
[h3]Wiki[/h3]
[list]
[*] [b]Add the toc option to the wiki[/b][/*]
The table of contents ([a]http://en.wikipedia.org/wiki/Table_of_contents | TOC[/a]) is a great option to preview the documentation structure and keep organized the documentation structure. Like the one on mediawiki :)
[*] [b]Improve wiki formatting[/b][/*]
[*] [i]Nested listing[/i][/*]
On some cases we need to list inside a list, currently this is not possible.
[*] [i]No formating text[/i][/*]
Currently the code tag can't disable some functions as URL Links, headers, listing, and other tags. So while trying to explain the usage of the tags it is not possible to show the "How should it writes" and "How will it look".
[*] [i]Tables[/i][/*]
Adding tables to the wiki would be great to organize information.
[*] [i]Quoting[/i][/*]
Good option for the Issues page than the wiki.
[*] [i]Comments[/i]?[/*]
Comments inside the wiki plain text for editors that are not displayed.
[/list]
[h2]h-client[/h2]
[list]
[*] [del]allow anonymous submission from the client[/del] (done!)[/*]
[p]Already implemented for the server[/p]
[*] [b]add the possibility to export the hardware configuration[/b][/*]
[p]Hardware working or not working to an xml file[/p]
[*] [b]add the possibility to load the hardware configuration from an xml
file[/b][/*]
[p][/p]
[*] [b]add the possibility to submit a whole xml file created by the client[/b][/*]
[p][/p]
[*] [b]add a [i]preview[/i] hardware tab/window on the client[/b][/*]
[p]Right now when the client is launched it gets you to the main page where it modifies the devices by just typing on the fields. Not pretty sure it's the best way of opening the client, since a bad move on the keyboard could imply unwanted changes to the database.[/p]
[p]The lspci -vmmnn search first sends a page where you can see if the hardware is already on the database and also tells you if it works or doesn't. If not present it will show an invitation to insert it.[/p]
[p]So maybe the first tab?/window? at the client should show a "[i]preview[/i]" of the hardware status, then invite to add/update the hardware found.[/p]
[*] [b]client l10n [/b][/*]
[p]Starting the localization of the client to the current supported by the project.
[*] English[/*]
[*] Español[/*]
[*] Italiano[/*]
[*] Français[/*]
[*] Deutsch[/*]
[/p]
[/list]
[h2]Mobile side[/h2]
[list]
[*] [b]write an application for the Replicant operating system[/b][/*]
[p]It would be nice to have the h-node application or something similar[/p]
[/list]
[h2]Others[/h2]
[list]
[*] ?[/*]
[/list]