[devel] Re: [criawips] some ideas...

[Adrien Beaucreux]

hi,

Le lun 05/07/2004 à 17:51, Sven Herzberg a écrit :
> > Since last week I managed to get it work, yeah. And even to begin to
> > understand part of the bable, yeah ! I'm tring (struggling) to also
> > understand the code, but I guess this is gonna be a bit longer to
> > achieve.
> 
>   Please remember that the first versions of criawips where just some
> small hacks that we intended to make the task of creating a text based
> slide easier and faster than it's been with magicpoint before.
> 
>   Lots of passages (especially the slide-show.c file) do really suck as
> they've been created to just display the stuff no matter how beautiful
> and maintainable the code was.
> 
>   I was rewriting the slide rendering stuff now (take a look at
> slide-view.c) to get some kind of maintainable rendering code into the
> CVS to be able to drop the ugly stuff from slide-show.c within the next
> weeks.

Please don't misunderstand me, I wasn't writing about the code quality,
that I can't appreciate, but about the fact that I'm not used to code
and trying to learn GObject/libgnome/libgnomeui/etc. It's quite a bit to
assimilate.

> > And I'm not sure I understand what you mean with this keyboard short-cut
> > thing.
> > 
> > What I mean with this plan is, we have teacher that specifically request
> > that one has the presentation plan somewhere on the screen at anytime,
> > with the fallacious pretext that it helps one to know how long he has to
> > suffer the current inane presentation.
> > 
> > Automate this come then quite handy.
> 
>   Please take a look at magicpoint, if you press <Ctrl> (IIRC) then a
> list of slides shows up at the bottom edge of the screen. Whether this
> should be displayed all the time or only on demand might become a
> configuration option.

Well, that's not what I'm thinking about. What you have is :

"01 02 03 04 ..." 

at the bottom of the screen. Not even close to talkative enough. 
"slide 3/23" is more compact and gives as much information. What I need
is more something like :

Introduction
MyFirstSection
  SlideOne
  SlideTwo
MySecondSection
  SlideThree
  SlideFour
Conclusion

I usually put it in a column on the left side of the screen, and the
current slide is highlighted in one way or another.

>   (This is a foreword to the upcoming paragraphs). At the moment,
> slides' XML does look quite ugly. One example:
> 
> <block title='content'>
>       &#8226; Hohe Qualität<br/><br/>&#8226; Leicht
> Benutzbar<br/><br/>&#8226; Jedem zugängig<br/>&#160;&#160;&#8226;
> Barrierefreiheit<br/>&#160;&#160;&#8226;
> Übersetzung<br/>&#160;&#160;&#8226; Usability
> </block>
> 
>   This is because the current XML parsing code is broken wrt white
> spaces. I already had a clear version of this, but unfortunately this
> one got lost.
> 
> > What i'm not fan about is to see in a slideshow :
> > 
> > >  <block title='content'>
> > >   &#8226; Hohe Qualität<br/>
> > >   <br />
> > >   &#8226; Leicht Benutzbar<br/>
> > >   <br />
> > >   &#8226; Jedem zugängig<br />
> > >   &#160;&#160;&#8226; Barrierefreiheit<br />
> > >   &#160;&#160;&#8226; Übersetzung<br />
> > >   &#160;&#160;&#8226; Usability
> > >  </block>
> 
>   This is a way that I think slides should be able to look like for
> version 0.0.6 (0.0.5 will introduce the display slide inside of the main
> window correctly stuff).
> 
> > It's not that clear. I'd think better to have :
> > 
> > >  <block title='content'>
> > >   <bulletlist>
> > >           <item>Hohe Qualität</item>
> > >           <item>Leicht Benutzbar</item>
> > >           <item>Jedem zugängig</item>
> > >           <bulletlist>
> > >                   <item>Barrierefreiheit</item>
> > >                   <item>Übersetzung</item>
> > >                   <item>Usability</item>
> > >           </bulletlist>
> > >   </bulletlist>
> > >  </block>
> > 
> > and somewhere defining that an item in a list begins by a &#8226;, and that
> > you have a &#160;&#160; indentation between 2 levels.
> > 
> > Thus you define tags such as <table> (This one you won't avoid, anyhow), 
> > <emphasize>, <list>, whatever.
> 
>   This stuff will require *lots* of refactoring and redesigning inside
> of the application. I know that we will need this structure some time in
> the future, but for simplicity of the code this stuff has been delayed.

Well, we can as well start to think about it, so we are prepared. You're
the expert here, but if you already know what's comming, won't it make
the refactoring less painful ? (newbie question...) As long as it
doesn't take much more efforts to do it later that now...

>   BTW, I don't plan to introduce <table> ever. Once we have a nice DOM
> and a clean MVC split we can work on embedding external data (images,
> diagrams, charts, tables, etc.), but I only want to embed tabled using
> gnumeric.

This one is an overkill. Not everyone has gnumeric. And loading gnumeric
to be able to print :

1       | blue
2       | green

well... I'm not fond of the idea, like killing flies with a cruise
missile.

Cheers,
Adrien