Hi Sergiu, On Sun, May 27, 2012 at 9:44 AM, Sergiu Dumitriu <[email protected]> wrote:
> On 05/11/2012 10:22 AM, Jerome Velociter wrote: > >> On Fri, May 11, 2012 at 4:14 PM, Vincent Massol<[email protected]> >> wrote: >> >>> >>> On Apr 30, 2012, at 2:28 AM, Sergiu Dumitriu wrote: >>> >>> On 04/25/2012 03:10 PM, Vincent Massol wrote: >>>> >>>>> Hi devs, >>>>> >>>>> Roadmap time again for 4.1. Here's a proposal below. If you're a >>>>> committer/contributor and wish to propose doing something for 4.1 please >>>>> reply to this thread to have a complete roadmap. >>>>> For committers who have their names next to tasks below, please >>>>> confirm you're ok to do that for 4.1. >>>>> >>>>> Dates >>>>> ====== >>>>> * Started since 16th of April >>>>> * 4.1M1: 7th of May >>>>> * 4.1M2: 28th of May >>>>> * 4.1RC1: 11th of June >>>>> * 4.1Final: 18th of June >>>>> >>>>> Release manager: Caleb, with help from Sergiu/Vincent >>>>> >>>>> Content >>>>> ======= >>>>> >>>>> XWiki SAS has had an internal meeting to discuss what it would like to >>>>> work on and here's the result as a proposal: >>>>> >>>>> Top level tasks: >>>>> >>>>> * Extension Manager (XEM compatibility, XAR merge UI, full XAR >>>>> upgrade) - Thomas and Marius >>>>> ** The goal is to be able to "upgrade a wiki farm in 5 minutes" for >>>>> 4.1 final >>>>> * Hidding Technical Content - Jean-Vincent >>>>> * Important JIRA issues - Sergiu and anyone having some time, see >>>>> below for the priority list >>>>> >>>>> Investigations: >>>>> * Home Page Changes Proposals - Caty >>>>> >>>>> Misc: >>>>> * GSOC mentoring - All mentors >>>>> >>>>> First priority JIRAs (no order): >>>>> >>>>> * Add the ability to auto-generate application entry names XWIKI-7374 >>>>> * Properly display live table columns based on User-type class fields >>>>> XWIKI-7372 >>>>> * Be able to rename a space from the UI XWIKI-6722 >>>>> >>>>> Second priority JIRAs (no order): >>>>> >>>>> * Add Required and Hint meta properties for class fields XWiki-7373 >>>>> * Generate and register a document bundle for the application >>>>> XWIKI-7371 >>>>> * Add document title and document content to the field palette (class >>>>> editor) XWIKI--7369 >>>>> * Use suggest input (custom display) for User and Group field types >>>>> (class editor) XWIKI-7368 >>>>> * Rename Application (through rename space) XWIKI-6722 >>>>> * OpenOffice Issues on Windows (bug) XWIKI-7510 >>>>> * Cannot filter using "/" on a Date column in the livetable XWIKI-5889 >>>>> * Auto-create Space.WebHome when creating a page in an underfined >>>>> space XWIKI-5399 >>>>> * New XWiki Syntax Guide XE-880 >>>>> * Occasionally the livetable fails to load on index pages XE-844 >>>>> * tag suggest feature does not work if Main.WebHome is not saved with >>>>> programming rights XE-539 >>>>> * Fix XWiki Installer on Windows 7 XE-1051 >>>>> * XWIKI-6073 Change stylesheet and javascript extension >>>>> filename when a modification is done on those Unassigned >>>>> >>>>> Third priority (no order): >>>>> * Add more/all configuration parameters in the wiki administration >>>>> XWIKI-7066 >>>>> * XWIKI-7510 XWiki is not able to automatically start >>>>> OpenOffice daemon on Windows Server Unassigned >>>>> * XWIKI-7509 XWiki automatically connect to an external >>>>> openoffice daemon Unassigned >>>>> * XWIKI-7058 Page creation date should be the date of the >>>>> installation Unassigned >>>>> * XWIKI-6951 When using filesystem attachments with attachment >>>>> versioning disabled, deleted attachments are duplicated on the hard disk. >>>>> CalebJamesDeLisle >>>>> * XWIKI-6917 Deleted attachments duplication in recycle bin >>>>> while File Storage is on CalebJamesDeLisle >>>>> * XWIKI-6892 Log-in automatically on registration Unassigned >>>>> * XWIKI-6569 Problems displaying the correct attachment >>>>> version when using a proxy Unassigned >>>>> * XWIKI-6363 Performance of blog category panel is still not >>>>> enough Unassigned >>>>> * XWIKI-6207 Auto-suggest doesn't work for global users >>>>> Unassigned >>>>> * XWIKI-5949 Better handling of different timezones for date >>>>> properties Jean-Vincent Drean >>>>> * XWIKI-5930 Activity Stream doesn't show Image Profile change >>>>> Unassigned >>>>> * XE-1031 Better placement of the documentation link >>>>> Unassigned >>>>> * XE-748 Add option to 'show more entries' on displaying >>>>> the Activity Stream Unassigned >>>>> >>>>> WDYT? >>>>> >>>> >>>> Sounds good, +1 from me. >>>> >>> >>> Sergiu, do you think you could help Marius by implementing the "Add the >>> ability to auto-generate application entry names - XWIKI-7374" for 4.1? >>> Marius is fully busy on the EM UI (especially the Merge UI). >>> >>> IMO what you could do if you agree would be to implement a new platform >>> module for autogenerating document names. >>> >> >> I know I've mentioned it already, but for potential inspiration in >> terms of use cases, you can checkout what I've done at >> https://github.com/jvelo/**xwiki-platform-pagecreation<https://github.com/jvelo/xwiki-platform-pagecreation>(and >> explained >> here: >> http://velociter.fr/different-**take-on-page-creation-in-xwiki<http://velociter.fr/different-take-on-page-creation-in-xwiki>) >> >> Jerome >> > > Hi devs, > > I've been working on this for a while, and here's the current status. > > I've looked at Jerome's code, and it looks like a very good starting > point, and it's actually almost ready to use. I've noticed that using a > sequence number isn't supported yet, but getting a proper safe sequence is > going to be hard to implement, so for the initial version I'm not going to > include support for sequence numbers. I've also did some minor tweaks and > bug fixes. > > I've looked at the current status of the AppWithinMinutes wizard, and I > think that the best way of integrating this new features is as a new step > (number 3), right after defining the class structure. This step would be > called "Documents", and here the user can define how the document title and > name is going to be defined. I'm not yet sure if exposing the document name > configuration is going to be confusing or not; to keep things simple, we > could just define one of them, the title, and let the name be the same as > the initial title, since most of the platform works fine with any character > in the document name. > > Without JavaScript, a simple form that fills in the values for Jerome's > PageCreation class is displayed. With Javascript, I envision an UI similar > to the structure step: the left side is the canvas on which the user can > drag pieces from a "toolbox" on the right side. The possible tools/pieces > will be: > > - a user entered text > - various date formats > - sequence number (when it will be implemented) > - the fields defined on the previous step, perhaps without large strings > - static text (by default a dash) > > The user can drag as many of these tokens as he wants, forming a chain. > Tokens can be re-arranged in this chain, or be removed. When hovering over > such a token, the same icons as on the form fields (from the previous step) > appear, letting the user drag, delete or edit that token. > > Editing a token means: > - setting a default value, a title, and a description for the "user > entered text" > - choosing among the predefined date formats (MMDDYY, YYYYMMDD, MMDD, > YYYYMMDD-HHMM, seconds since epoch) or writing a custom format (too > advanced?) > - choosing the minimum width of the sequence number (how many decimals to > print, prefixing with 0) > - nothing for class fields? Any ideas? > - the value of the static text to insert > > I've looked at inserting a new step in the AWM wizard, and I was a bit > disappointed to see that the three wizard steps are tightly linked > together, making it very hard to add new steps in between. I changed things > a bit to make it easier to insert new steps in the future, although it's > far from perfect. At least we don't assume that there are always three > steps. And I inserted this new step in the wizard, for the moment with the > non-js UI; still working on the JS enhancements. > > Next, when creating new documents, instead of the simple input asking for > the title, the form will display all the required inputs, or, if no input > is needed, jump straight to the document. > > Does that sound like what's needed? > Yes, I think it does. It might even be more that what's needed for a first version of this to be usable. > Things are starting to get in shape, I expect to have everything ready by > the end of next week. Did you commit anything yet? I'd love to test this feature. Guillaume -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > ______________________________**_________________ > devs mailing list > [email protected] > http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/mailman/listinfo/devs> > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
