Re: new ostream code
On Mon, Mar 13, 2000 at 03:15:33AM +0100, Lars Gullik Bjnnes wrote: Very well. Are you expanding on/using the langague struct that I added? Lgb Yes. (BTW, the member leftTOright in struct Language should be RightToLeft, but don't change it as I've already changed it in my patch)
Re: new ostream code
On Mon, Mar 13, 2000 at 03:15:33AM +0100, Lars Gullik Bjnnes wrote: > Very well. Are you expanding on/using the langague struct that I > added? > > Lgb Yes. (BTW, the member leftTOright in struct Language should be RightToLeft, but don't change it as I've already changed it in my patch)
Re: new ostream code
Dekel Tsur [EMAIL PROTECTED] writes: | On Wed, Mar 08, 2000 at 05:46:37AM +0100, Lars Gullik Bjønnes wrote: | | After that is done, I think we should have a new prerelease to get a | broader userbase to have a look. (This will perhaps also be a nice | time for rae to update again?) I'll put in some cvs tags. | | | But there are still some reported bugs that haven't been fixed! | | Furthermore, I'm currently changing the Hebrew support to a general language | support: the LyXFont class is now storing a pointer to a Language structure | (instead of storing the direction). I want to finish this change and include | it in the sources before the prerelease (since I've changed the file format | for Hebrew documents, and I don't want an "official" version to use the old | format) Very well. Are you expanding on/using the langague struct that I added? Lgb
Re: new ostream code
On Wed, Mar 08, 2000 at 05:46:37AM +0100, Lars Gullik Bjnnes wrote: After that is done, I think we should have a new prerelease to get a broader userbase to have a look. (This will perhaps also be a nice time for rae to update again?) I'll put in some cvs tags. But there are still some reported bugs that haven't been fixed! Furthermore, I'm currently changing the Hebrew support to a general language support: the LyXFont class is now storing a pointer to a Language structure (instead of storing the direction). I want to finish this change and include it in the sources before the prerelease (since I've changed the file format for Hebrew documents, and I don't want an "official" version to use the old format)
Re: new ostream code
Dekel Tsur <[EMAIL PROTECTED]> writes: | On Wed, Mar 08, 2000 at 05:46:37AM +0100, Lars Gullik Bjønnes wrote: | > | > After that is done, I think we should have a new prerelease to get a | > broader userbase to have a look. (This will perhaps also be a nice | > time for rae to update again?) I'll put in some cvs tags. | > | | But there are still some reported bugs that haven't been fixed! | | Furthermore, I'm currently changing the Hebrew support to a general language | support: the LyXFont class is now storing a pointer to a Language structure | (instead of storing the direction). I want to finish this change and include | it in the sources before the prerelease (since I've changed the file format | for Hebrew documents, and I don't want an "official" version to use the old | format) Very well. Are you expanding on/using the langague struct that I added? Lgb
Re: new ostream code
On Wed, Mar 08, 2000 at 05:46:37AM +0100, Lars Gullik Bjnnes wrote: > > After that is done, I think we should have a new prerelease to get a > broader userbase to have a look. (This will perhaps also be a nice > time for rae to update again?) I'll put in some cvs tags. > But there are still some reported bugs that haven't been fixed! Furthermore, I'm currently changing the Hebrew support to a general language support: the LyXFont class is now storing a pointer to a Language structure (instead of storing the direction). I want to finish this change and include it in the sources before the prerelease (since I've changed the file format for Hebrew documents, and I don't want an "official" version to use the old format)
Re: new ostream code
On 8 Mar 2000, Lars Gullik Bjønnes wrote: I will begin slowly to remove the code that is dead when USE_OSTREAM_ONLY is defined. Pending bugreports I am going to do that in the next two-three days. After that is done, I think we should have a new prerelease to get a broader userbase to have a look. (This will perhaps also be a nice time for rae to update again?) I'll put in some cvs tags. That would indeed be not only convenient but very good timing. If all goes to my secret plan my branch could be merged into the main trunk by late next week. Another prelease about a week later. Then again maybe I should hold off on merging gui-indep until after 1.1.5? GUI initialization is likely to stay in lyx_gui.C until we have gotten further down the track with other gui toolkits. Otherwise it gets even more awkward trying to get xforms initialized for the LyXViews and the other toolkit/s for the dialogs. Allan. (ARRae)
Re: new ostream code
Allan Rae [EMAIL PROTECTED] writes: | Another prelease about a week later. | | Then again maybe I should hold off on merging gui-indep until after | 1.1.5? Yes, we should wait till after 1.1.5 before merging the rae branch. Lgb
Re: new ostream code
On 8 Mar 2000, Lars Gullik Bjønnes wrote: > > I will begin slowly to remove the code that is dead when > USE_OSTREAM_ONLY is defined. Pending bugreports I am going to do that > in the next two-three days. > > After that is done, I think we should have a new prerelease to get a > broader userbase to have a look. (This will perhaps also be a nice > time for rae to update again?) I'll put in some cvs tags. That would indeed be not only convenient but very good timing. If all goes to my secret plan my branch could be merged into the main trunk by late next week. > Another prelease about a week later. Then again maybe I should hold off on merging gui-indep until after 1.1.5? GUI initialization is likely to stay in lyx_gui.C until we have gotten further down the track with other gui toolkits. Otherwise it gets even more awkward trying to get xforms initialized for the LyXViews and the other toolkit/s for the dialogs. Allan. (ARRae)
Re: new ostream code
Allan Rae <[EMAIL PROTECTED]> writes: | > Another prelease about a week later. | | Then again maybe I should hold off on merging gui-indep until after | 1.1.5? Yes, we should wait till after 1.1.5 before merging the rae branch. Lgb
new ostream code
I will begin slowly to remove the code that is dead when USE_OSTREAM_ONLY is defined. Pending bugreports I am going to do that in the next two-three days. After that is done, I think we should have a new prerelease to get a broader userbase to have a look. (This will perhaps also be a nice time for rae to update again?) I'll put in some cvs tags. Fix bugs reported. Another prelease about a week later. Fix bugs reported. Unless something serious. Release lyx 1.1.5 about a week after the last prerelease. Ok, this is my gameplan for the next 2.5 weeks. Lgb
new ostream code
I will begin slowly to remove the code that is dead when USE_OSTREAM_ONLY is defined. Pending bugreports I am going to do that in the next two-three days. After that is done, I think we should have a new prerelease to get a broader userbase to have a look. (This will perhaps also be a nice time for rae to update again?) I'll put in some cvs tags. Fix bugs reported. Another prelease about a week later. Fix bugs reported. Unless something serious. Release lyx 1.1.5 about a week after the last prerelease. Ok, this is my gameplan for the next 2.5 weeks. Lgb
