[Lumiera] [CodingStatus] Summer 2009

[andrew]

Hi,

Related to the status code is the site Lumiera hypertext. The site 
Lumiera is in a process redesign.

The process redesign involves, conversions documents to asciidoc, review 
documents, proposals redesign, restructure store git, style site 
hypertext, uWiki. The process described is order chronological 
approximately. Some parts of the process may interdepend.

I have summarized redesign as two types, that should facilitate and 
divide discussion per expertise:

    * structure store git
    * style hypertext

The structure store git is defined is the folds, files at 
http://www.lumiera.org/gitweb?p=website;a=tree. The style hypertext is 
defined as what you see in browser hypertext like firefox at lumiera.org.

All authors should mail proposals to the list lumiera at lists.lumiera.org. 
Include any media to convey the design, text, graphic ... are most useful.

    I think we should advertise request for proposals at lumiera.org. I
    want to do something like the site where the logo Lumiera was
    created. As the site hypertext is in transition, is the site
    pipapo.org is easiest to serve the proposals? Except we should limit
    use of pipapo.org, as its use for the project Lumiera is discontinued.

Since the last message redesign, a summary:

    * some documents from the tiddlywiki were converted to format asciidoc
    * no documents asciidoc were reviewed
    * some proposals design
          o style hypertext, author is nezza-_-
    * some restructure store is temporary
    * no restyle hypertext, send your proposals
    * uWiki, refer to messages prior from Christian Thaeter (most recent
      is attached)


A description detailed of the process conversion from tiddlywiki to 
asciidoc is at
http://www.lumiera.org/gitweb?p=website-work/andrew;a=summary
/wiki/tiddlywiki2asciidoc/tiddlywiki2asciidoc.txt


Christian Thaeter wrote:
> Ichthyostega wrote:
>   
>> Hello all,
>>
>> on our September IRC developer meeting we concluded it should be desirable to
>> write a summary of coding achievements on a regular base. People interested in
>> Lumiera pointed out that it's difficult for an interested non-programmer to
>> figure out what actually happened beyond t-shirts and propaganda posters.
>> They noticed GIT logs, but those are completely arcane to an outsider.
>>
>> Thus the idea is for the developers to write draft summary items from time
>> to time. At the moment, these summary items should just be posted to the
>> Mailinglist. We should strive at understandability for an technically
>> inclined non-coder (Sorry, no geeks, no frogs and no grandma).
>> Averagely on a quarterly base, these summary drafts should be
>> compiled into a news item for the website.
>>
>> We'd need the help by volunteers for the latter task.
>>
>> Cheers,
>> Hermann V.
>>
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> This spring, to conclude the transformation of the GUI into a loadable Plug-in,
>> Joel and myself undertook a design study featuring a mock playback facility.
>> The underlying problem with all those topics is to get the separated parts work
>> together without tangling them, thereby effectively killing pluggability.
>>
>> In a similar vein, Joel and I determined that the next big topic to address
>> would be getting the GUI connected to the high-level model within Proc.
>> Currently, the GUI uses ad-hoc placeholder interfaces, and there is just an
>> emerging model backbone in Proc. Progress in GUI is currently somewhat blocked
>> by this lack of an reliable reference point. Joel used the time to improve the
>> docking library Lumiera relies on (and besides, he's gotten a new job and
>> foremost needed to concentrate on that).
>>
>> Meanwhile, I devised the parts intended to form this GUI-Proc connection,
>> including the interface of an index facility to be implemented within the
>> high-level model. The latter included design work on the series of "scopes"
>> a placement (of an MObject) will use for lookup of any value not defined
>> immediately in-object. Moreover, at some point I deemed it necessary to
>> interrupt to work on the frontend of a command system, serving to dispatch
>> any operation initiated from the GUI cleanly into the Proc-Layer. Btw, the
>> backend of this command system will work together with serialiser (loading
>> / storing objects persistently) and UNDO-manager. Besides. I should mention
>> some interspersed work on the builder interfaces and the low-level model.
>>
>> At the same time, Christian worked on his non-interactive debugging library
>> NoBug, with the goal to complete a sort-of 1.0 release (reached recently).
>> Lumiera heavily relies on this library for logging, diagnosis and detection
>> of misaligned resource handling. Besides, there was significant work done
>> on uWiki. Christian, could you please give a summary of the situation there?
>>     
>
> NoBug is now in a 'polishing' phase I expect to do few releases next
> weeks with things fixed/improved but feature wise it is (almost)
> complete. Benny (a NoBug contributor not here on the list) working on
> it. So it won't be a big timesink for me and be shiny quite soon.
>
> Teld, Mridkash and Digitalkiwi worked on uWiki, but it is kindof stucked
> because of no one has enough time and/or experience to work contiguously
> on it to lead it to a first working state. Since the last NoBug release
> I am now working on uwiki to give it that kick, thats delays my work on
> Lumiera a bit more unfortunately. I hope to get it working seriously
> within the next 1-2 weeks, but there is quite some work to do, maybe
> *You* consider to help us instead blaming us for slow progress :P
> As sidenote I was quite surprised that uWiki stirred a lot interest at
> FrOSCon and I am confident that as soon it lifts of we have a fair
> chance to get programmers and contributors then. The only problem
> currently is to give it enough momentum to go over the first hill which
> means it should be very basic usable and put online.
>
> As soon as possible I am then back working on the Lumiera backend, there
> are tons of things to do there. There was no much progress because of
> the above things, but on the bright side, when I left off there, quite
> some things ready or in a basically usable state:
>  * Plugin loading and interface system works (still lacks lot of
>    features), its usable enough to work with it
>  * the Config/Preferences system is also working in a restricted way,
>    but usable enough for now. Simav working on improving it.
>  * Basic File handling in the backend is working, the higher level
>    stuff to make caches and media file access including indexing and
>    stuff is not ready yet, that will be where I continue next.
>  * Thread management is in a mockup, but working state.
>
>
> 	Christian
> _______________________________________________
> Lumiera mailing list
> Lumiera at lists.lumiera.org
> http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
>
>
>