On 17 Aug 2000, Lars Gullik Bjønnes wrote:
> Baruch Even <[EMAIL PROTECTED]> writes:
>
> | It might be a good idea to release soon a lyx-1.1.6-beta1 in order to do
> | the testing by those who will need to use the code. It would be a bad idea
> | to release so much new code without having some brave users test it
> | beforehand,
>
> We always have at lest three prereleases if tere have been a lot of
> changes, so the questions if we should push forward and go direcly
> for the 1.2.0 goal, or stop up a bit and release 1.1.6pre1 (and we
> have work that is needed for that too...), if we don't release a
> 1.1.6pre we enable the NEW_TABULAR and NEW_INSETS wait a bit, fix
> stuff implement some, and release a 1.2.0pre1
I think that taking a break now will be a good idea, we could then try to
aim for better support for GUII in 1.2.0, as far as I looked into it, it
will require quite a bit of work to get LyX fully GUII, quite a bit of its
internals are dependent on X windows calls.
> How far is the graphics inset from working with eps files with all
> transformations? Is it equiv. with the figureinset?
It is equivalent to figinset in all except the inline viewing, it even
surpasses it IMNSHO, mainly due to the removal of the first dialog that
asks to inline or not (this dialog is now in the main dialog, a far better
solution).
The inline viewing still requires quite a bit of work, the problem is that
XForms 0.88 to the best of my knowledge will not load any image format. I
need to use XPM's, Ghostscript cannot output XPM's so I'm out of luck
here. It will require implementing a conversion facility from PNG to XPM,
not too bad but I want to do this thing right (or at least mostly right)
from the start.
There is quite a bit of polish that is needed by the inset itself and the
inline viewing, I'll need to go over the code, rewrite some, remove some
and polish it all so that it will be in a good state, but that can be done
easily. It really is nothing big.
If you (and the others) won't mind adding a dependency on imlib for the
time being for the use of inline viewing, I can most probably accomplish
it all in under three weeks, possibly two. This will mean that those who
don't have imlib will not have inline viewing, but they will be able to
use LyX without a trouble besides that.
Anyhow, until I won't have a real replacement to the FigInset, in terms of
inline viewing, the graphics inset should be used as an addition for those
who need it (for PDF production f.ex.) and not as a replacement, one main
reason this is so is that the graphics inset doesn't yet have a figinset
reader, only the native reader so it images using fig inset are loaded as
such, and the two insets can work together in a single document (I believe
I tried that in the beginning of my work, haven't tried that for some time
now though).
> The minipage inset and the float insets need some work, but not a lot.
I have no idea about those :-)
My knowledge in LyX is now in the graphics inset, GUII and possibly later
I'll join the Gnome porting project, I'd really like a gLyX version :-)
> We don't need to be have any enhanced support for 1.2.0, but to be no
> worse than 1.1.5.
This is the usual wish of software development.
--
Baruch Even
http://techst02.technion.ac.il/~sbaruch/ (My Site)
http://rpghost.com/jindor/ (My brothers AD&D site)
" Learn to laugh ... it's the path to true love! "
- The Angel in the movie Michael
